You might encounter the following message when you attempt to log on to SAS OpRisk VaR:

SAS Connection Failure: VaR administrative account is not configured correctly.
  
Please contact your system administrator.

This message is usually accompanied by the following Java traceback details:

java.lang.Exception: SAS Connection Failure: VaR administrative account is not
configured correctly.
Please contact your system administrator.
at com.sas.oprisk.var.core.CLogin.processLogin(CLogin.java:191)
at com.sas.oprisk.var.core.CLogin.access$000(CLogin.java:37)
at com.sas.oprisk.var.core.CLogin$1.execute(CLogin.java:89)
at com.sas.oprisk.var.core.worker.Worker$1.run(Worker.java:39)
at java.lang.Thread.run(Thread.java:534)

There are a few possible causes for this error. First, ensure that the SAS OpRisk VaR administrative user is correctly set up:

• The administrative user must be granted all permissions for the Data Store.



• The administrative user must be correctly specified on the Application Properties tab in the Configuration Editor.



• To verify that the administrative user is correctly specified, open the Configuration Editor and do the following:
  
  
  1. Go to the Application Properties tab and click the Load Properties button to open the Connection Information window.
  
  
  
  2. In the Connection Information window, fill out the form with the host name, port number, path, and user information that is necessary to access the Data Store.
  
  
  
  3. In the SAS OpRisk VaR Administrator section of the Application Properties tab, make sure that the Username value for the SAS OpRisk VaR administrative user is correct.



• For further verification, open the VAR_PROPERTIES table and check the VarAdmin1 and VarAdmin2 values. This table is located in the base directory of the Data Store. VarAdmin1 should contain the administrative user and VarAdmin2 should contain an encoded password for that user. These values are specified on the Application Properties tab of the Configuration Editor.

If a SHARE Server is being used then it is also necessary to specify the Root Libname in ALL UPPERCASE letters. Open the Configuration Editor → in the Root Libname field for the SHARE Server, and ensure that the value is in all uppercase letters. For example, use VARDATA instead of vardata or VarData. Remember to save any changes so that the updates are applied to the opriskvar.ini file. This updated opriskvar.ini file must then be deployed to each SAS OpRisk VaR client. This is done by copying the updated opriskvar.ini to the SAS OpRisk VaR installation directory on each SAS OpRisk VaR client machine. For example, the default SAS OpRisk VaR 3.2 installation directory on Windows is 'C:\Program Files\SAS\SASOpRiskVaR\3.2'. It is good practice to back up the existing opriskvar.ini file before replacing it with the newly-updated opriskvar.ini file.

Operating System and Release Information